Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1102

reference: 757-tree-1
name: 1102
tree-preservation-order: undefined
757-tpo-1
uprn
address-text
point: POINT (-1.010678 50.888322)
geometry: MULTIPOLYGON (((-1.010621 50.888316,-1.010624 50.888327,-1.010632 50.888337,-1.010644 50.888345,-1.010660 50.888350,-1.010677 50.888352,-1.010695 50.888350,-1.010711 50.888346,-1.010724 50.888338,-1.010732 50.888328,-1.010735 50.888317,-1.010733 50.888305,-1.010725 50.888295,-1.010712 50.888287,-1.010697 50.888282,-1.010679 50.888280,-1.010661 50.888282,-1.010645 50.888287,-1.010633 50.888295,-1.010624 50.888305,-1.010621 50.888316)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL